Docs Issue 7455: add 'export' keyword to code snippet#7456
Docs Issue 7455: add 'export' keyword to code snippet#7456AmanVarshney01 merged 1 commit intoprisma:mainfrom
Conversation
WalkthroughThis pull request corrects a code example in the Prisma 7 upgrade documentation by adding the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
👋 Hi @csrs! Thanks for your contribution to the Prisma docs. We wanted to let you know that we've recently updated our documentation structure and guidelines. Your PR may need to be updated to align with these changes. Action needed:
|
Resolves prisma#7455 The PostgreSQL adapter "After" code snippet was missing the `export` keyword on the `prisma` variable, inconsistent with the SQLite example directly below it.
|
@AmanVarshney01 is attempting to deploy a commit to the Prisma Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks for the PR @csrs 🫡 |
Resolves #7455
In this code snippet https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7#after-1, the last line is missing the export keyword.
Currently:
Proposed change:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.